Skip to content

Remove duplicate label-check job from CI workflow#87

Merged
bharvey88 merged 1 commit into
ApolloAutomation:betafrom
bharvey88:fix/ci-drop-label-check
Jul 14, 2026
Merged

Remove duplicate label-check job from CI workflow#87
bharvey88 merged 1 commit into
ApolloAutomation:betafrom
bharvey88:fix/ci-drop-label-check

Conversation

@bharvey88

Copy link
Copy Markdown
Contributor

Version: N/A (workflow-only, does not publish)

What does this implement/fix?

Removes the redundant label-check job from ci.yml. It duplicates the standalone label-check.yml (which runs on pull_request_target) and always fails on fork-submitted PRs, because pull_request grants forks a read-only token that cannot apply labels. This is the failing "Label Check" people have been seeing on fork PRs.

Also trims the now-unneeded pull-requests: write / issues: write permissions. This matches the already-clean ci.yml on MSR-1 and CAST-1's main.

Types of changes

  • Bugfix (fixed change that fixes an issue)
  • New feature (thanks!)
  • Breaking change (repair/feature that breaks existing functionality)
  • Dependency Update - Does not publish
  • Other - Does not publish
  • Website of github readme file update - Does not publish
  • Github workflows - Does not publish

Checklist / Checklijst:

  • The code change has been tested and works locally
  • The code change has not yet been tested

If user-visible functionality or configuration variables are added/modified:

  • Added/updated documentation for the web page

🤖 Generated with Claude Code

The label-check job in ci.yml duplicates label-check.yml and, because
ci.yml runs on plain pull_request, always fails on fork-submitted PRs
where the token is read-only and cannot apply labels. label-check.yml
already handles this on pull_request_target. Drop the redundant job and
the now-unneeded pull-requests/issues write permissions, matching the
already-clean main on MSR-1 and CAST-1.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@bharvey88, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5fe3ce63-026b-49b5-923c-6412fe8e3a41

📥 Commits

Reviewing files that changed from the base of the PR and between 4c0f31d and 09399b5.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@bharvey88
bharvey88 merged commit 64b884b into ApolloAutomation:beta Jul 14, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant